Skip to content

feat(SpaceAndTime): Fourier transform derivatives - #2101

Open
gloges wants to merge 12 commits into
leanprover-community:masterfrom
gloges:wvs-fourier-deriv
Open

gloges wants to merge 12 commits into
leanprover-community:masterfrom
gloges:wvs-fourier-deriv

Conversation

@gloges

@gloges gloges commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Adds the necessary machinery to get to derivatives of fourierIntegral and fourierIntegralInv (both Fréchet and partial):

  • Refactors the definitions of fourierIntegral(Inv) to use Real.fourierChar (first commit). This makes co-opting results from VectorFourier.fourierIntegral easier.
  • Explicit NormedSpace instance for WaveVectorSpace (needed for the same reasons as for Space).
  • Operator norms and continuity properties of the dual functionals.
  • Fourier integrals of continuous linear maps.
  • Continuous linear maps fourier(Inv)SMulRight which arise naturally in the fderiv of the (inverse) Fourier integral and their basic properties.

@gloges
gloges marked this pull request as ready for review November 17, 2026 01:15
@github-actions

github-actions Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Thank you for this pull-request (PR). If this is your first PR, welcome to the community!

While you wait for a review, note that you can review PRs too; reviewing is not restricted to maintainers. Our review guidelines explain what to look for.

Over time, contributions such as reviews, maintenance and documentation are recorded on contributions.physlib.io.

Three main points:

  • Comment -awaiting-author on its own line to remove that label from your PR.
  • Comment blocked-by-PR or -blocked-by-PR on its own line to add or remove that label, respectively.
  • The first review might take several days to arrive. If in doubt message on the Zulip.

For the author: Please read

Below is what will happen next. Please read carefully if you are not familiar with the process. You may open other PRs while this one is being reviewed, and can stack PRs on top of each other, so don't let these steps slow you down.

  1. Some automated checks will be run on your PR. You can see the results of these checks at the buttom of your PR page. If any of these checks fail, you will need to fix the issues before your PR can be merged. You can learn more about these here, including how to run them locally, which is sometimes quicker than relying on the GitHub Actions. If you have never had a PR merged before, you may have to wait for a reviewer to manually start these checks (this is for security).

  2. A reviewer will look at your PR and may ask you to make changes. This may happen a couple of days after you submit your PR, so you may need to be patient. But it should not be longer than that - if it is please bring it to the attention of the community on the Zulip. The level of review will depend on where your PR is submitted. If it is submitted to ./Physlib or ./QuantumInfo, the review will be more thorough than if it is submitted to ./PhyslibAlpha. You can find out more about what the review process is looking for in our review guidelines. If a reviewer adds an awaiting-author label to your PR, address the review comments, then please remove that label by adding a comment with -awaiting-author. This helps us keep track of reviews.

  3. The reviewer will either approve your PR, or request more changes (in which case we return to step 2). Once your PR is approved, it will be merged by a maintainer, this should happen shortly after approval, though you may get more comments at this stage.

Tip: The easiest way to get a fast review is to submit a PR that is small and self-contained, and has clear documentation explaining why things are the way they are in your changes.

If you have any problems or questions, please reach out to the community on the Zulip.

For reviewers: Summary of your PR

Found differences:
@@ Physlib.SpaceAndTime.WaveVectorSpace.Basic @@
! module modified Physlib.SpaceAndTime.WaveVectorSpace.Basic (+8 -0)
  namespaces WaveVectorSpace
+ added instance : NormedSpace ℝ (WaveVectorSpace d)
@@ Physlib.SpaceAndTime.WaveVectorSpace.DualPairing @@
! module modified Physlib.SpaceAndTime.WaveVectorSpace.DualPairing (+34 -0)
  namespaces Space, WaveVectorSpace
+ added lemma _root_.Space.continuous_dual
+ added lemma continuous_dual
+ added lemma opNorm_dual_eq_norm
+ added lemma opNorm_dual_eq_norm
+ added lemma pairingCLM_apply_apply
@@ Physlib.SpaceAndTime.WaveVectorSpace.Fourier @@
! module modified Physlib.SpaceAndTime.WaveVectorSpace.Fourier (+192 -33)
  namespaces WaveVectorSpace, FourierTransform, FourierTransform.FourierTransform1n1
+ added def fourierInvSMulRight
+ added def fourierSMulRight
+ added lemma aestronglyMeasurable_fourierInvSMulRight
+ added lemma aestronglyMeasurable_fourierSMulRight
+ added lemma deriv_fourierIntegral
+ added lemma deriv_fourierIntegralInv
+ added lemma fderiv_fourierIntegral
+ added lemma fderiv_fourierIntegralInv
+ added lemma fourierIntegralInv_continuousLinearMap_apply
+ added lemma fourierIntegral_continuousLinearMap_apply
+ added lemma fourierInvSMulRight_apply
+ added lemma fourierInvSMulRight_eq
+ added lemma fourierSMulRight_apply
+ added lemma fourierSMulRight_eq
+ added lemma integrable_fourierInvSMulRight
+ added lemma integrable_fourierSMulRight
+ added lemma opNorm_fourierInvSMulRight
+ added lemma opNorm_fourierSMulRight
- removed def physChar
- removed lemma physChar_continuous
29 differences

The declarations are found by reading the diff as text, without regard for namespaces, so a declaration whose keyword and name are on different lines is missed, and two declarations of the same name in different namespaces are listed as one. A change to a proof, or to the body of a definition, does not appear. See scripts/alpha/github/pr_summary.lean.

Summary of commit 1af59bd, remade whenever a commit is pushed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant